-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 Add examples and bundles section #618
Conversation
✅ Deploy Preview for kairos-io ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
I'll leave the webui docs once we have a release for it |
Just some rephrasing left and we are good to go |
Opened #627 for the webui docs |
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
|
||
Kairos supports three types of bundles: | ||
|
||
- *Container*: This type is a bare container that simply contains files that need to be copied to the system. It is useful for copying over configuration files, scripts, or any other static content that you want to include on your system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about bold instead of italics?
|
||
- *Package*: This type is a [luet](https://luet.io) package that will be installed in the system. It requires the luet repository definition in order to work. Luet packages are a powerful way to manage dependencies and install software on your system. | ||
|
||
Note: In the future, Kairos will also support a local type for use in airgap situations, where you can pre-add bundles to the image before deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe put this in an alert?
@@ -45,7 +45,7 @@ c58930881bc4: Pushed | |||
... | |||
``` | |||
|
|||
You can use your custom image with the `kairos-agent upgrade` command, or with the [system-upgrade-controller in Kubernetes](/docs/upgrade/kubernetes). Here's how to use the `kairos-agent` command: | |||
You can use your custom image when [upgrade nodes manually](/docs/upgrade/manual), [with Kubernetes](/docs/upgrade/kubernetes) or [specifying it in the cloud-config during installation](/docs/examples/core). Here's how to do it manually with the `kairos-agent` command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe when upgrading nodes manually
?
|
||
bundles: | ||
- targets: | ||
- run://<image> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the <image>
used here is the same as the tag in 123 but if I understand correctly here i need the full path e.g. quay.io/kairos/community-bundles:metallb_latest
- We set `install.image` to the container image that we want to deploy. This can be an image from [our support matrix](/docs/reference/image_matrix), a [custom image](/docs/advanced/customizing) or an [image from scratch](/docs/reference/build). | ||
- After the installation is complete, the configuration in the `k3s` block will take effect. This is because after the installation, the system will boot into the image specified in the `install.image` field, which in the example above is an image with the Kairos K3s provider, as such the configuration in the k3s block will become active. | ||
|
||
With these steps, you should now be able to use Kairos core images as an installer to deploy other container images. The process is straightforward and gives you the flexibility to customize your deployments and build custom images as needed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this also mean that we can now make the provider images smaller, providing only the additional files, excluding the OS filesystem already provided by the core image?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we could - however we should start to think about implications during upgrades if we go down that path
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and for that I'd rather have an interface around CAPI to handle all of this transparently, but we aren't there yet
|
||
We will use the [k3s manifest method](/docs/reference/configuration#kubernetes-manifests) to deploy `MetaLB`. | ||
|
||
To get started, you'll need to use the [provider-kairos](https://github.com/kairos-io/provider-kairos) artifacts, which include k3s. We'll be using the [k3s manifest method](/docs/reference/configuration#kubernetes-manifests) to deploy MetalLB. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
backlink to the "bundle" method as an alternative?
args: | ||
- --disable=traefik,servicelb | ||
|
||
# Additional manifests that are applied by k3s on boot |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This part has nothing to do with the single node cluster setup right? I think we already demonstrated this metallb setup here: https://github.com/kairos-io/kairos/pull/618/files#diff-e23d6395ab8483864c81358c557904814cd5a78f16193e2b086363638a188fde
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Mauro Morales <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]>
Signed-off-by: mudler <[email protected]>
Signed-off-by: mudler <[email protected]>
Re-adapted to your feedback @jimmykarily and @mauromorales 👍 |
* 📖 Add examples Signed-off-by: mudler <[email protected]> * 📖 Add Bundles docs Signed-off-by: mudler <[email protected]> * 📖 Update config reference for p2p block Signed-off-by: mudler <[email protected]> * 📖 Add Fedora and Debian images, update status Signed-off-by: mudler <[email protected]> * 📖 Add bundles and core sections Signed-off-by: mudler <[email protected]> * 📖 Rephrase Signed-off-by: mudler <[email protected]> * 📖 Rephrase Signed-off-by: mudler <[email protected]> * 📖 Add p2p samples Signed-off-by: mudler <[email protected]> * 📖 Rephrase Signed-off-by: mudler <[email protected]> * 📖 Rephrase Signed-off-by: mudler <[email protected]> * Update docs/content/en/docs/Advanced/bundles.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/multi-node-p2p-ha-kubevip.md Co-authored-by: Mauro Morales <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/bundles.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/multi-node-p2p-ha-kubevip.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/multi-node-p2p.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/multi-node.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/multi-node-p2p-ha.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Examples/single-node.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * Update docs/content/en/docs/Reference/configuration.md Co-authored-by: Dimitris Karakasilis <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> * 📖 Review Signed-off-by: mudler <[email protected]> * 📖 Review Signed-off-by: mudler <[email protected]> Signed-off-by: mudler <[email protected]> Signed-off-by: Ettore Di Giacinto <[email protected]> Co-authored-by: Dimitris Karakasilis <[email protected]> Co-authored-by: Mauro Morales <[email protected]>
Signed-off-by: mudler [email protected]
Fixes: #48
Adds examples:
example
section (link toadvanced/build
, copy-paste example)